Disk utilization analysis

ABSTRACT

An approach is provided for monitoring disk utilization at an object level. At a first time a first size of an object (i.e., integrated file system or library) in a System i computing platform is determined. At a second time a second size of the object is determined. A difference between the first and second sizes is determined. The difference is determined to be greater than a threshold. Based on the difference exceeding the threshold, an alert is sent indicating growth at the object level rather than at an auxiliary storage pool level. Sizes of System i libraries are monitored at multiple dates and stored in a repository. Sizes of the libraries at user-entered start and end dates are retrieved from the repository. Differences between the sizes of the libraries at the start and end dates are determined and presented.

This application is a continuation application claiming priority to U.S.Ser. No. 14/597,551 filed Jan. 15, 2015.

TECHNICAL FIELD

The present invention relates to managing utilization of computerresources, and more particularly to automatic object level monitoring ofdisk utilization.

BACKGROUND

Known disk utilization monitoring techniques for systems running the IBMi operating system utilize auxiliary storage pool (ASP)-levelmonitoring. An ASP is a group of disk drives in a System i® (also knownas iSeries®) platform. The grouping of disk drives in an ASP organizesdata to limit the impact of storage device failures and to reducerecovery time. If a disk failure occurs, only the data in the ASPcontaining the failed unit needs to be recovered. ASPs may also isolateobjects with similar performance attributes, thereby improvingperformance. In the System i® platform, it is typical for all diskdrives to be assigned to a single ASP. The System i® and iSeries®platforms are computer system platforms offered by InternationalBusiness Machines Corporation located in Armonk, New York. System i® andiSeries® are registered trademarks of International Business MachinesCorporation.

ASP-level monitoring tracks an increase in size of disk utilization atthe level of the ASP, but not at the level of an actual library orobject created on top of the ASP. Known monitoring of disk utilizationat the ASP level is a manual approach, which includes logging onto theSystem i® ASP to analyze which library or object caused the monitoredincrease in the size of the ASP.

Generating a spooled disk utilization report using the known diskutilization monitoring techniques takes a significant amount of time,typically four to 17 hours, thereby making real time disk utilizationdata unavailable. Generating the disk utilization report use thePRTDIRINF/RTVDIRINF commands and/or the PRTDSKINF/RTVDSKINF commands.The PRTDIRINF (also known as (a.k.a.) Print Directory Information)command prints attributes of objects in the integrated file system,where the attributes of the objects are collected by the RTVDIRINF(a.k.a. Retrieve Directory Information) command. The PRTDSKINF (a.k.a.Print Disk Information) command prints disk space information that wasstored in a database file by the RTVDSKINF (a.k.a. Retrieve DiskInformation) command.

Because of the significant amount of time to generate the diskutilization report using known techniques, the analysis of the diskutilization data must be delayed, which increases a risk of outages orfailure to obtain objectives of service level agreements.

BRIEF SUMMARY

In a first embodiment, the present invention provides a method ofmonitoring disk utilization at an object level. The method includes acomputer determining at a first time a first size of an object in aSystem i® platform by calling an application programming interface(API). The object is (1) an object in an integrated file system (IFS) or(2) a library that includes other objects which are named storage spacesin the System i® platform. The method further includes the computerdetermining at a second time a second size of the object by calling theAPI. The second time is subsequent to the first time and the second sizeis greater than the first size. The method further includes the computerdetermining a difference between the first and second sizes. The methodfurther includes the computer determining the difference exceeds athreshold difference. The method further includes based on thedifference exceeding the threshold difference, the computer sending analert about the object having a growth in size that exceeds thethreshold difference. The alert indicates the growth at a level of theobject, which is different from a growth at a level of an auxiliarystorage pool in the System i® platform.

In a first aspect of the present invention, the steps of determining thefirst size of the object and the second size of the object do not employthe commands RTVDSKINF, PRTDSKINF, RTVDIRINF, or PRTDIRINF.

In a second aspect of the present invention, the method further includesthe computer periodically and automatically monitoring sizes of objectsin the IFS, which determines sizes of the objects in the IFS at multipledates, and which stores the sizes of the objects in the IFS at multipledates in a data repository. The method further includes the computerreceiving via an interface a selection by a user of a comparison ofsizes of the objects in the IFS at a start date and an end date. Themethod further includes the computer receiving via the interface thestart date and the end date entered by the user. The start and end datesare included in the multiple dates. The method further includes thecomputer retrieving from the data repository the sizes of the objects atthe start and end dates. The method further includes the computerdetermining differences between the sizes of the objects at the startdate and respective sizes of the objects at the end date. The methodfurther includes the computer presenting the differences and the sizesof the objects at the start and end dates. The method further includesthe computer generating and sending a report that includes thedifferences and the sizes of the objects at the start and end dates.

In a third aspect of the present invention, the method further includesthe computer periodically and automatically monitoring sizes oflibraries in the System i® platform, which determines sizes of thelibraries at multiple dates, and which stores the sizes of the librariesat the multiple dates in a data repository. The method further includesthe computer receiving via an interface a selection from a user of acomparison of sizes of the libraries at a start date and an end date.The method further includes the computer receiving via the interface thestart date and the end date entered by the user. The start and end datesare included in the multiple dates. The method further includes thecomputer retrieving from the data repository the sizes of the librariesat the start and end dates. The method further includes the computerdetermining differences between the sizes of the libraries at the startdate and respective sizes of the libraries at the end date. The methodfurther includes the computer presenting the differences and the sizesof the objects at the start and end dates. The method further includesthe computer generating and sending a report that includes thedifferences and the sizes of the objects at the start and end dates.

In a fourth aspect of the present invention, the method further includesthe computer receiving via an interface a selection by a user of a realtime comparison of sizes of objects in an integrated file system (IFS)in the System i® platform at a start date and a current time. The methodfurther includes the computer receiving via the interface the start dateentered by the user. The method further includes the computer calling anapplication programming interface (API) in the System i® platform, whichobtains the sizes of the objects at the start date and the current time.The method further includes the computer determining differences betweenthe sizes of the objects at the start date and respective sizes of theobjects at the current time. The method further includes the computerpresenting the differences and the sizes of the objects at the startdate and the current time. The method further includes the computergenerating and sending a report that includes the differences and thesizes of the objects at the start date and the current time.

In a fifth aspect of the present invention, the method further includesthe computer receiving via an interface a selection from a user of areal time comparison of sizes of libraries at a start date and a currenttime. The method further includes the computer receiving via theinterface the start date entered by the user. The method furtherincludes the computer calling an application programming interface (API)in the System i platform, which obtains the sizes of the libraries atthe start date and the current time. The method further includes thecomputer determining differences between the sizes of the libraries atthe start date and respective sizes of the libraries at the currenttime. The method further includes the computer presenting thedifferences and the sizes of the objects at the start date and thecurrent time. The method further includes the computer generating andsending a report that includes the differences and the sizes of theobjects at the start date and the current time.

In a sixth aspect of the present invention, the steps of determining thefirst and second sizes, determining the difference do not includemanually logging onto a system in the System i platform to determine thefirst and second sizes.

In a second embodiment, the present invention provides a computer systemincluding a central processing unit (CPU); a memory coupled to the CPU;and a computer-readable storage device coupled to the CPU. The storagedevice includes instructions that are executed by the CPU via the memoryto implement a method of automatically monitoring disk utilization at anobject level. The method includes the computer system determining at afirst time a first size of an object in a System i® platform by callingan application programming interface (API). The object is (1) an objectin an integrated file system (IFS) or (2) a library that includes otherobjects which are named storage spaces in the System i® platform. Themethod further includes the computer system determining at a second timea second size of the object by calling the API. The second time issubsequent to the first time and the second size is greater than thefirst size. The method further includes the computer system determininga difference between the first and second sizes. The method furtherincludes the computer system determining the difference exceeds athreshold difference. The method further includes based on thedifference exceeding the threshold difference, the computer systemsending an alert about the object having a growth in size that exceedsthe threshold difference. The alert indicates the growth at a level ofthe object, which is different from a growth at a level of an auxiliarystorage pool in the System i® platform.

In a third embodiment, the present invention provides a computer programproduct including a computer-readable storage device and acomputer-readable program code stored in the computer-readable storagedevice. The computer-readable program code includes instructions thatare executed by a central processing unit (CPU) of a computer system toimplement a method of monitoring disk utilization at an object level.The method includes the computer system determining at a first time afirst size of an object in a System i® platform by calling anapplication programming interface (API). The object is (1) an object inan integrated file system (IFS) or (2) a library that includes otherobjects which are named storage spaces in the System i® platform. Themethod further includes the computer system determining at a second timea second size of the object by calling the API. The second time issubsequent to the first time and the second size is greater than thefirst size. The method further includes the computer system determininga difference between the first and second sizes. The method furtherincludes the computer system determining the difference exceeds athreshold difference. The method further includes based on thedifference exceeding the threshold difference, the computer systemsending an alert about the object having a growth in size that exceedsthe threshold difference. The alert indicates the growth at a level ofthe object, which is different from a growth at a level of an auxiliarystorage pool in the System i® platform. In a fourth embodiment, thepresent invention provides a method of monitoring disk utilization at anobject level. The method includes the computer presenting a first optionto select a comparison of sizes of objects in an integrated file system(IFS) in the System i® platform at first and second times and a secondoption to select a comparison of sizes of libraries in the System iplatform at the first and second times. The method further includes thecomputer receiving a selection from a user of the first option or thesecond option. The method further includes the computer receiving thefirst time as a user entry of a start date. The method further includesthe computer either (1) receiving the second time as a user entry of anend date or (2) determining the second time as a current time inresponse to the user selecting a third option to indicate the comparisonof sizes of objects in the IFS or the comparison of sizes of librariesis a real time comparison. The method further includes if the selectionof the first option was received and the user entry of the end date wasreceived: (1) the computer retrieving from a data repository the sizesof the objects at the start and end dates, where the sizes of theobjects at the start and end dates had been previously stored byperiodic monitoring of the sizes of the objects; (2) the computerdetermining differences between the sizes of the objects at the startdate and respective sizes of the objects at the end date; and (3) thecomputer generating and sending a report that includes the differencesand the sizes of the objects at the start and end dates. The methodfurther includes if the selection of the second option was received andthe user entry of the end date was received: (1) the computer retrievingfrom a data repository the sizes of the libraries at the start and enddates, where the sizes of the libraries at the start and end dates hadbeen previously stored by periodic monitoring of the sizes of thelibraries; (2) the computer determining differences between the sizes ofthe libraries at the start date and respective sizes of the libraries atthe end date; and (3) the computer generating and sending a report thatincludes the differences and the sizes of the objects at the start andend dates. The method further includes if the selection of the firstoption was received and the second time was determined to be the currenttime: the computer calling the first API, which obtains the sizes of theobjects at the start date and the current time; the computer determiningdifferences between the sizes of the objects at the start date andrespective sizes of the objects at the current time; and the computergenerating and sending a report that includes the differences and thesizes of the objects at the start date and the current time. The methodfurther includes if the selection of the second option was received andthe second time was determined to be the current time: the computercalling the second API, which obtains the sizes of the libraries at thestart date and the current time; the computer determining differencesbetween the sizes of the libraries at the start date and respectivesizes of the libraries at the current time; and the computer generatingand sending a report that includes the differences and the sizes of theobjects at the start date and the current time.

In a fifth embodiment, the present invention provides a method ofmonitoring disk utilization at an object level. The method includes acomputer determining at a first time a first size of an object bycalling an application programming interface (API) provided by acomputing platform. The object is (1) a directory in a hierarchical filesystem provided by the computing platform, or (2) a library thatincludes other objects which are named storage spaces in the computingplatform. The method further includes the computer determining at asecond time a second size of the object by calling the API. The secondtime is subsequent to the first time and the second size is greater thanthe first size. The method further includes the computer determining adifference between the first and second sizes. The method furtherincludes the computer determining the difference exceeds a thresholddifference. The method further includes based on the differenceexceeding the threshold difference, the computer sending an alert aboutthe object having a growth in size that exceeds the thresholddifference. The alert indicates the growth at a level of the object.

Embodiments and aspects of the present invention summarized aboveprovide a quick and automated approach for monitoring object sizeinformation and reporting the information within one hour or less. Anautomated email facility allows an alert and/or a report to beautomatically emailed if object size growth over a specified time periodexceeds a predefined threshold value for relative change or relativepercentage change over the specified time period.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system for monitoring disk utilization atan object level, in accordance with embodiments of the presentinvention.

FIG. 2 is a flowchart of a process of monitoring disk utilization at anobject level, where the process is implemented in the system of FIG. 1,in accordance with embodiments of the present invention.

FIGS. 3A-3B depict a flowchart of a process for determining a sizecomparison for libraries or integrated file system objects, where theprocess is implemented in the system of FIG. 1, in accordance withembodiments of the present invention.

FIG. 4 is an example of a display including a start date-to-end datecomparison of sizes of libraries resulting from the process of FIGS.3A-3B, in accordance with embodiments of the present invention.

FIG. 5 is an example of a display including a real time comparison ofsizes of libraries resulting from the process of FIGS. 3A-3B, inaccordance with embodiments of the present invention.

FIG. 6 is an example of a display including a start date-to-end datecomparison of sizes of directories resulting from the process of FIGS.3A-3B, in accordance with embodiments of the present invention.

FIG. 7 is an example of a display including a real time comparison ofsizes of directories resulting from the process of FIGS. 3A-3B, inaccordance with embodiments of the present invention.

FIG. 8 is a block diagram of a computer that is included in the systemof FIG. 1 and that implements the processes of FIG. 2 and FIGS. 3A-3B,in accordance with embodiments of the present invention.

DETAILED DESCRIPTION

Overview

Embodiments of the present invention utilize system APIs and systemprograms to automatically track the growth of individual objects definedin a System i® platform, quickly determine whether any of the objectshave experienced a sudden and excessive growth in size, andautomatically send alerts about objects that have experienced sudden andexcessive growth in size. Embodiments of the present invention determinegrowth in the size of individual libraries and/or individual IFS objects(e.g., directories) in a system in one hour or less, rather than thefour to 17 hours taken to determine growth of ASPs in the same systemusing known techniques. By quickly identifying one or more particularobjects and the associated jobs that are responsible for excessivegrowth in size, embodiments allow a review of the type of data involvedin the excessive growth and a determination whether the type of dataindicates the data can be deleted. For example, review of a report maydetermine that an object exhibiting excessive and sudden growth is atemporary object created during patch management, which may be safelydeleted. If the type of data indicates application data is causing theexcessive growth in size, then the reports or alerts generated byembodiments of the present invention allow owners of the applicationdata to be queried about whether the application data may be safelydeleted. By addressing the excessive growth through deletion of data,embodiments of the present invention prevent situations in which growthin size of ASPs beyond critical limits cause a computer system to behaveunpredictably or to shut down and require a costly and time-consumingrestart during which business is negatively impacted. Embodimentsdiscussed herein do not utilize the RTVDIRINF, PRTDIRINF, RTVDSKINF, orPRTDSKINF commands used by known techniques for disk utilizationanalysis.

As used herein, a library is defined as a system object that serves as adirectory to other objects. A library groups related objects, and allowsa user to find objects by name. In the System i® platform, thesystem-recognized identifier for the object type of a library is *LIB.An object is defined as is a named storage space that consists of a setof characteristics that describe itself and, in some cases, data. Anobject is anything that exists in and occupies space in storage and onwhich operations can be performed. Some examples of objects in a libraryare programs, files, and folders.

As used herein, an IFS object is an object that is organized in thehierarchical directory structure provided by IFS. A directory is aspecial IFS object that is used to locate objects by names. Eachdirectory contains a list of objects that are attached to it. The listof objects may include one or more other directories.

System for Monitoring Disk Utilization at an Object Level

FIG. 1 is a block diagram of a system 100 for monitoring diskutilization at an object level, in accordance with embodiments of thepresent invention. System 100 includes a computer 102, which executes asoftware-based disk analyzer tool 104. In one embodiment, computer 102is a System i® computer running the IBM i® operating system. Diskanalyzer tool 104 accesses ASPs 106-1, . . . , 106-N, where N is aninteger greater than or equal to one, and utilizes system programs andAPIs to determine the sizes of objects included in the ASPs. The objectsincluded in the ASPs are libraries and/or IFS objects, such asdirectories. ASP 106-1 includes object 108-1, . . . , object 108-K,where K is an integer greater than or equal to one. ASP 106-N includesobject 110-1, . . . , object 110-M, where M is an integer greater thanor equal to one.

Disk analyzer tool 104 determines and monitors the sizes of theaforementioned objects (i.e., libraries or IFS objects) at successivetimes which are separated by predetermined time intervals. Disk analyzertool 104 stores in data repository 111 the sizes of the aforementionedobjects and the respective times at which the sizes were determined.Disk analyzer tool 104 determines the difference between the sizes ofeach object at the successive times, determines whether the differenceexceeds a predetermined threshold difference, and sends an alert 112 ifthe difference between sizes of the object at the successive timesexceeds the threshold difference. As used herein, a difference betweensizes is a relative difference between the sizes or a relativepercentage difference between the sizes. The threshold difference may bea threshold relative difference or a threshold relative percentagedifference such as 5%.

In response to a user command for a disk utilization report and entry ofa start date and an end date, disk analyzer tool 104 determines thesizes of objects at the start date and the end date, and for eachobject, determines the difference between the sizes at the start and enddates. Disk analyzer tool 104 generates and presents a report 114, whichincludes the name of each object, the size at the start date, the sizeat the end date, and the difference between the sizes at the start andend dates.

In response to a user command for a real time disk utilization report,and an entry of a start date, disk analyzer tool 104 determines thesizes of objects at the start date and at the current time, and for eachobject, determines the difference between the sizes at the start dateand the current time. Disk analyzer tool 104 generates and presentsreport 114 which includes the name of each object, the size at the startdate, the size at the current time, and the difference between the sizesat the start date and the current time.

The functionality of the components of FIG. 1 is described in moredetail in the discussions presented below relative to FIG. 2, FIGS.3A-3B, and FIG. 8.

Process for Monitoring Disk Utilization at an Object Level

FIG. 2 is a flowchart of a process of monitoring disk utilization at anobject level, where the process is implemented in the system of FIG. 1,in accordance with embodiments of the present invention. The process ofFIG. 2 begins at step 200. Prior to step 202, disk analyzer tool 104(see FIG. 1) receives a threshold difference. In one embodiment, priorto step 202, disk analyzer tool 104 (see FIG. 1) receives a timeinterval, which is the frequency at which disk analyzer tool 104monitors the sizes of objects (i.e., libraries and/or IFS objects) inASP 106-1, . . . , 106-N (see FIG. 1). For example, if the received timeinterval is one day, then disk analyzer tool 104 (see FIG. 1) determinesthe sizes of the objects once each day.

In step 202, disk analyzer tool 104 (see FIG. 1) determines at a firsttime a first size of an object in a System i® platform (i.e., an objectincluded in object 108-1, . . . , object 108-K (see FIG. 1) . . . object110-1, . . . , object 110-M (see FIG. 1)). The object is a library or anIFS object. To determine the first size of the object, disk analyzertool 104 (see FIG. 1) calls system programs and one or more APIs. In oneembodiment, disk analyzer tool 104 (see FIG. 1) calls the followingAPIs: QLIRLIBD to determine the size of a single library and QSRSRV todetermine sizes of directories and sub-directories. In step 202, diskanalyzer tool 104 (see FIG. 1) also stores the first size of the objectand the first time in a database record or another data structure indata repository 111 (see FIG. 1).

In step 204, disk analyzer tool 104 (see FIG. 1) determines at a secondtime a second size of the object by again calling the system programsand API(s). The second time is subsequent to the first time. In oneembodiment, the amount of time between the first and second times isequal to the time interval received by disk analyzer tool 104 (seeFIG. 1) prior to step 202. In step 204, disk analyzer tool 104 (seeFIG. 1) also stores the second size of the object and the second time ina database record or another data structure in data repository 111 (seeFIG. 1).

In step 206, disk analyzer tool 104 (see FIG. 1) determines a differencebetween the first and second sizes. In the first iteration of theprocess of FIG. 2, the first and second sizes are determined in the mostrecent performances of steps 202 and 204, respectively. In subsequentiterations, the second size is determined in the most recent performanceof step 204 and the first size is determined in step 214, which isdescribed below.

In step 208, disk analyzer tool 104 (see FIG. 1) determines whether thedifference determined in step 206 exceeds the threshold difference. Ifdisk analyzer tool 104 (see FIG. 1) determines in step 208 that thedifference exceeds the threshold difference, then the Yes branch of step208 is taken and step 210 is performed.

In step 210, based on the difference exceeding the threshold difference,disk analyzer tool 104 (see FIG. 1) sends alert 112 (see FIG. 1) (e.g.,by e-mail) about the object having a growth in size between the firstand second times that exceeds the threshold difference (i.e., the objecthas experienced a sudden and excessive growth in size).

In step 212, disk analyzer tool 104 (see FIG. 1) determines whethermonitoring of object sizes is to be continued. If disk analyzer tool 104(see FIG. 1) determines in step 212 that monitoring is to be continued,then the Yes branch of step 212 is followed and step 214 is performed.

In step 214, disk analyzer tool 104 (see FIG. 1) prepares for the nextiteration of the process of FIG. 2 by setting the value of the firsttime in the next iteration to be the second time in the currentiteration, and setting the value of the first size in the next iterationto become the second size in the current iteration. Following step 214,the next iteration of the process of FIG. 2 starts at step 204, with thedetermination of the second size at the second time.

Returning to step 212, if disk analyzer tool 104 (see FIG. 1) determinesthat monitoring is not to be continued, then the No branch of step 212is followed, and the process of FIG. 2 ends at step 216.

Returning to step 208, if disk analyzer tool 104 (see FIG. 1) determinesthat the difference does not exceed the threshold difference, then theNo branch of step 208 is taken and the process of FIG. 2 continues withstep 212, as described above.

In one embodiment, the sizes of multiple objects in system 100 (seeFIG. 1) are monitored by using the steps of the process of FIG. 2 foreach of the multiple objects.

In an alternate embodiment, in an alternate to step 202, disk analyzertool 104 (see FIG. 1) determines at a first time a first size of anobject by calling an API provided by a non-System i® computing platformwhich is a Unix® , IBM® AIX ® , or Microsoft® Windows® platform, or amainframe platform such as System/390®. The object is (1) a directory ina hierarchical file system provided by the computing platform, or (2) alibrary that includes other objects which are named storage spaces inthe computing platform. Disk analyzer tool 104 (see FIG. 1) stores thefirst size in data repository 111 (see FIG. 1). In an alternate to step204, disk analyzer tool 104 (see FIG. 1) determines at a second time asecond size of the object by calling the API. The second time issubsequent to the first time and the second size is greater than thefirst size. Disk analyzer tool 104 (see FIG. 1) stores the second sizein data repository 111 (see FIG. 1). The descriptions of steps 206, 208,210, 212, 214 and 216 presented above also apply to the alternateembodiment discussed in this paragraph.

FIGS. 3A-3B depict a flowchart of a process for determining a sizecomparison for libraries or integrated file system objects, where theprocess is implemented in the system of FIG. 1, in accordance withembodiments of the present invention. The process of FIGS. 3A-3B startsat step 300. In step 302, disk analyzer tool 104 (see FIG. 1) receives aselection from a user to perform either (1) a comparison of sizes oflibraries or (2) a comparison of sizes of IFS objects. If disk analyzertool 104 (see FIG. 1) receives a selection to perform the comparison ofsizes of libraries, the LIBRARY branch of step 302 is taken and step 304is performed.

In step 304, disk analyzer tool 104 (see FIG. 1) determines whether aselection by the user was received for a real time comparison of sizesof libraries, rather than a comparison of sizes of the libraries at astart date and an end date that precede the current time. If diskanalyzer tool 104 (see FIG. 1) determines in step 304 that the user didnot select a real time comparison of sizes, then the No branch of step304 is taken and step 306 is performed.

In step 306, disk analyzer tool 104 (see FIG. 1) receives the start andend dates from user entries on an interface provided by disk analyzertool 104 (see FIG. 1).

In step 308, disk analyzer tool 104 (see FIG. 1) retrieves from datarepository 111 (see FIG. 1) the sizes of the libraries at the start andend dates, where the start and end dates were received in step 306. Inone embodiment, the API called in step 308 is QLIRLIBD in the System i®platform.

In step 310, disk analyzer tool 104 (see FIG. 1) determines the actualand relative differences between the sizes of the libraries at the startand end dates. In one embodiment, the relative difference between thesizes of a library at the start and end dates is a relative percentagedifference equal to (actual difference between the sizes/size of thelibrary at the start date)×100%.

In step 312, disk analyzer tool 104 (see FIG. 1) displays or otherwisepresents the differences and sizes of the libraries at the start and enddates.

In step 314, optional user selections and entries on the interfacecauses disk analyzer tool 104 (see FIG. 1) to sort the informationpresented in step 312 (e.g., by the sizes of the libraries at the enddate, the name of the library, or the differences in the sizes) and/orto search the information presented in step 312 by the name or partialname of the library. Another optional user selection causes diskanalyzer tool 104 (see FIG. 1) to present details of objects that areincluded within a user-selected library. The details of objects mayinclude their names, sizes, types, creation dates, identifiers of thecreators, and dates of the changes made.

In step 316, an optional user selection on the interface causes diskanalyzer tool 104 (see FIG. 1) to generate report 114 (see FIG. 1) as aspool file report and to send report 114 (see FIG. 1) to one or morepredetermined email addresses. The report includes names of thelibraries, sizes of the libraries at the start and end dates, anddifferences between the sizes.

In step 318, which follows step 316, the process of FIGS. 3A-3B ends.

Returning to step 304, if disk analyzer tool 104 (see FIG. 1) determinesthat the user selected a real time comparison of sizes of libraries,then the Yes branch of step 304 is taken and step 320 is performed.

In step 320, disk analyzer tool 104 (see FIG. 1) receives the start datefrom a user entry on the interface.

In step 322, disk analyzer tool 104 (see FIG. 1) obtains sizes of thelibraries at the start date received in step 320 and at the currenttime. Disk analyzer tool 104 (see FIG. 1) in step 322 obtains the sizesof the libraries at the current time by one or more calls to an API. Inone embodiment, the API called in step 322 is QLIRLIBD in the System i®platform. Disk analyzer tool 104 (see FIG. 1) in step 322 obtains thesizes of the libraries at the start date by retrieving the sizes fromdata repository 111 (see FIG. 1).

In step 324, disk analyzer tool 104 (see FIG. 1) determines the actualand relative differences between the sizes of the libraries at the startdate and at the current time. In one embodiment, the relative differencebetween the sizes of a library at the start date and the current time isa relative percentage difference equal to (actual difference between thesizes/size of the library at the start date)×100%.

In step 326, disk analyzer tool 104 (see FIG. 1) displays or otherwisepresents the differences determined in step 324 and the sizes of thelibraries at the start date and at the current time.

In step 328, optional user selections and entries on the interfacecauses disk analyzer tool 104 (see FIG. 1) to sort the informationpresented in step 326 (e.g., by the sizes of the libraries at thecurrent time, the name of the library, or the differences in the sizes)and/or to search the information presented in step 326 by the name orpartial name of the library. Another optional user selection causes diskanalyzer tool 104 (see FIG. 1) to present details of objects that areincluded within a user-selected library. The details of objects mayinclude their names, sizes, types, creation dates, identifiers of thecreators, and dates of changes made.

In step 330, an optional user selection on the interface causes diskanalyzer tool 104 (see FIG. 1) to generate report 114 (see FIG. 1) as aspool file report and to send report 114 (see FIG. 1) to one or morepredetermined email addresses. The report includes names of thelibraries, sizes of the libraries at the start date and the currenttime, and differences between the sizes. Following step 330, the processof FIGS. 3A-3B ends at step 318.

Returning to step 302, if disk analyzer tool 104 (see FIG. 1) receives aselection to perform the comparison of sizes of IFS objects, the IFSbranch of step 302 is taken and step 332 in FIG. 3B is performed.

In step 332, disk analyzer tool 104 (see FIG. 1) determines whether aselection by the user was received for a real time comparison of sizesof IFS objects, rather than a comparison of sizes of the IFS objects ata start date and an end date that precede the current time. If diskanalyzer tool 104 (see FIG. 1) determines in step 332 that the user didnot select a real time comparison of sizes, then the No branch of step332 is taken and step 334 is performed.

In step 334, disk analyzer tool 104 (see FIG. 1) receives the start andend dates from user entries on an interface provided by disk analyzertool 104 (see FIG. 1).

In step 336, disk analyzer tool 104 (see FIG. 1) retrieves from datarepository 111 (see FIG. 1) the sizes of the IFS objects at the startand end dates, where the start and end dates were received in step 334.In one embodiment, the API called in step 336 is QSRSRV in the Systemplatform.

In step 338, disk analyzer tool 104 (see FIG. 1) determines the actualand relative differences between the sizes of the IFS objects at thestart and end dates. In one embodiment, the relative difference betweenthe sizes of an IFS object at the start and end dates is a relativepercentage difference equal to (actual difference between the sizes/sizeof the IFS object at the start date)×100%.

In step 340, disk analyzer tool 104 (see FIG. 1) displays or otherwisepresents the differences and sizes of the IFS objects at the start andend dates.

In step 342, optional user selections and entries on the interfacecauses disk analyzer tool 104 (see FIG. 1) to sort the informationpresented in step 340 (e.g., by the sizes of the IFS objects at the enddate, the name of the IFS object, or the differences in the sizes)and/or to search the information presented in step 340 by a name orpartial name of an IFS object.

In step 344, an optional user selection on the interface causes diskanalyzer tool 104 (see FIG. 1) to generate report 114 (see FIG. 1) as aspool file report and to send report 114 (see FIG. 1) to one or morepredetermined email addresses. The report includes names of the IFSobjects, sizes of the IFS objects at the start and end dates, anddifferences between the sizes.

The process of FIGS. 3A-3B ends at step 346, which follows step 344.

Returning to step 332, if disk analyzer tool 104 (see FIG. 1) received auser selection of a real time comparison of sizes of IFS objects, thenthe Yes branch of step 332 is taken and step 348 is performed.

In step 348, disk analyzer tool 104 (see FIG. 1) receives the start datefrom a user entry on an interface provided by disk analyzer tool 104(see FIG. 1).

In step 350, disk analyzer tool 104 (see FIG. 1) obtains sizes of theIFS objects at the start date received in step 352 and at the currenttime. Disk analyzer tool 104 (see FIG. 1) in step 350 obtains the sizesof the IFS objects at the current time by one or more calls to an API.In one embodiment, the API called in step 350 is QSRSRV in the System i®platform. Disk analyzer tool 104 (see FIG. 1) in step 350 obtains thesizes of the IFS objects at the start date by retrieving the sizes fromdata repository 111 (see FIG. 1).

In step 352, disk analyzer tool 104 (see FIG. 1) determines the actualand relative differences between the sizes of the IFS objects at thestart date and the current time. In one embodiment, the relativedifference between the sizes of an IFS object at the start date and thecurrent time is a relative percentage difference equal to (actualdifference between the sizes/size of the IFS object at the startdate)×100%.

In step 354, disk analyzer tool 104 (see FIG. 1) displays or otherwisepresents the differences and sizes of the IFS objects at the start andend dates.

In step 356, optional user selections and entries on the interfacecauses disk analyzer tool 104 (see FIG. 1) to sort the informationpresented in step 354 (e.g., by the sizes of the IFS objects at thecurrent time, the name of the IFS object, or the differences in thesizes) and/or to search the information presented in step 354 by a nameor partial name of an IFS object.

In step 358, an optional user selection on the interface causes diskanalyzer tool 104 (see FIG. 1) to generate report 114 (see FIG. 1) as aspool file report and to send report 114 (see FIG. 1) to one or morepredetermined email addresses. The report includes names of the IFSobjects, sizes of the IFS objects at the start date and the currenttime, and differences between the sizes.

The process of FIGS. 3A-3B ends at step 346, which follows step 358.

EXAMPLES

FIG. 4 is an example of a display 400 including a start date-to-end datecomparison of sizes of libraries resulting from the process of FIGS.3A-3B, in accordance with embodiments of the present invention. Display400 is a report that includes a start date of Oct. 6, 2014, an end dateof Oct. 7, 2014, library names, sizes of the libraries at the start andend dates, absolute differences between the sizes of the libraries atthe start and end dates (i.e., the values under the column labeled“Difference”), and relative percentage differences between the sizes atthe start and end dates (i.e., the values under the column labeled “%Difference”). For example, for the library named QASDLIB1, display 400includes a size of 49,975 MB at the start date, a size of 56,422 MB atthe end date, an absolute difference of 6,447 MB (i.e., the size at theend date−the size at the start date, or 56,422 MB-49,975 MB), and arelative percentage difference of 12.90% (i.e., (the absolute differencedivided by the size of the library at the start date)×100%, or (6,447MB/49,975 MB)×100%). Display 400 is an example of the report generatedin step 316 (see FIG. 3A).

FIG. 5 is an example of a display 500 including a real time comparisonof sizes of libraries resulting from the process of FIGS. 3A-3B, inaccordance with embodiments of the present invention. Display 500 is areport that includes a start date of Oct. 6, 2014 and a current time of19:05:22 on Oct. 8, 2014. Display 500 further includes library names,sizes of the libraries at the start date and current time (i.e., thevalues under the columns labeled “Start Date” and “End Date”,respectively), absolute differences between the sizes of the librariesat the start date and the current time (i.e., the values under thecolumn labeled “Difference”), and relative percentage differencesbetween the sizes at the start date and current time (i.e., the valuesunder the column labeled “% Difference”). For example, for the librarynamed QUSRSYS, display 500 includes a size of 210,284 MB at the startdate, a size of 616,570 MB at the current time, an absolute differenceof 406,286 MB (i.e., the size at the current time−the size at the startdate, or 616,570 MB−210,284 MB), and a relative percentage difference of193.20% (i.e., (the absolute difference divided by the size of thelibrary at the start date)×100%, or (406,286 MB/210,284 MB)×100%).Display 500 is an example of the report generated in step 330 (see FIG.3A).

FIG. 6 is an example of a display 600 including a start date-to-end datecomparison of sizes of directories resulting from the process of FIGS.3A-3B, in accordance with embodiments of the present invention. Display600 is a report that includes a start date of Oct. 6, 2014, an end dateof Oct. 7, 2014, directory names, sizes of the directories at the startand end dates, absolute differences between the sizes of the directoriesat the start and end dates (i.e., the values under the column labeled“Difference”), and relative percentage differences between the sizes ofthe directories at the start and end dates (i.e., the values under thecolumn labeled “% Difference”). For example, for the directory namedERRORS, display 600 includes a size of 49 MB at the start date, a sizeof 50 MB at the end date, an absolute difference of 1 MB (i.e., the sizeat the end date−the size at the start date, or 50 MB−49 MB), and arelative percentage difference of 2.04% (i.e., (the absolute differencedivided by the size of the directory at the start date)×100%, or (1MB/49 MB)×100%). Display 600 is an example of the report generated instep 344 (see FIG. 3B).

FIG. 7 is an example of a display 700 including a real time comparisonof sizes of directories resulting from the process of FIGS. 3A-3B, inaccordance with embodiments of the present invention. Display 700 is areport that includes a start date of Oct. 6, 2014 and a current time of19:22:27 on Oct. 8, 2014. Display 700 further includes directory names,sizes of the directories at the start date and current time (i.e., thevalues under the columns labeled “Start Date” and “End Date”,respectively), absolute differences between the sizes of the directoriesat the start date and current time (i.e., the values under the columnlabeled “Difference”), and relative percentage differences between thesizes at the start date and current time (i.e., the values under thecolumn labeled “% Difference”). For example, for the directory namedERRORS, display 700 includes a size of 49 MB at the start date, a sizeof 53 MB at the current time, an absolute difference of 4 MB (i.e., thesize at the current time−the size at the start date, or 53 MB−49 MB),and a relative percentage difference of 8.16% (i.e., (the absolutedifference divided by the size of the directory at the start date)×100%,or (4 MB/49 MB)×100%). Display 700 is an example of the report generatedin step 358 (see FIG. 3B).

Computer System

FIG. 8 is a block diagram of a computer that is included in the systemof FIG. 1 and that implements the processes of FIG. 2 and FIGS. 3A-3B,in accordance with embodiments of the present invention. Computer 102 isa computer system that generally includes a central processing unit(CPU) 802, a memory 804, an input/output (I/O) interface 806, and a bus808. Further, computer 102 is coupled to I/O devices 810 and a computerdata storage unit 812. CPU 802 performs computation and controlfunctions of computer 102, including carrying out instructions includedin program code 814 to perform a method of monitoring disk utilizationat an object level, where the instructions are carried out by CPU 802via memory 804. CPU 802 may include a single processing unit, or bedistributed across one or more processing units in one or more locations(e.g., on a client and server). Program code 814 includes program codefor the software-based components of computer 102, such as disk analyzertool 104 (see FIG. 1).

Memory 804 includes a known computer readable storage medium, which isdescribed below. In one embodiment, cache memory elements of memory 804provide temporary storage of at least some program code (e.g., programcode 814) in order to reduce the number of times code must be retrievedfrom bulk storage while instructions of the program code are carriedout. Moreover, similar to CPU 802, memory 804 may reside at a singlephysical location, including one or more types of data storage, or bedistributed across a plurality of physical systems in various forms.Further, memory 804 can include data distributed across, for example, alocal area network (LAN) or a wide area network (WAN).

I/O interface 806 includes any system for exchanging information to orfrom an external source. I/O devices 810 include any known type ofexternal device, including a display device, keyboard, etc. Bus 808provides a communication link between each of the components in computer102, and may include any type of transmission link, includingelectrical, optical, wireless, etc.

I/O interface 806 also allows computer 102 to store information (e.g.,data or program instructions such as program code 814) on and retrievethe information from computer data storage unit 812 or another computerdata storage unit (not shown). Computer data storage unit 812 includes aknown computer-readable storage medium, which is described below. In oneembodiment, computer data storage unit 812 is a non-volatile datastorage device, such as a magnetic disk drive (i.e., hard disk drive) oran optical disc drive (e.g., a CD-ROM drive which receives a CD-ROMdisk).

Memory 804 and/or storage unit 812 may store computer program code 814that includes instructions that are carried out by CPU 802 via memory804 to monitor disk utilization at an object level. Although FIG. 8depicts memory 804 as including program code 814, the present inventioncontemplates embodiments in which memory 804 does not include all ofcode 814 simultaneously, but instead at one time includes only a portionof code 814.

Further, memory 804 includes an operating system (not shown) and mayinclude other systems not shown in FIG. 8. In one embodiment, theoperating system is the IBM® i operating system.

Storage unit 812 and/or one or more other computer data storage units(not shown) that are coupled to computer 102 may include ASP 106-1, . .. , ASP 106-N (see FIG. 1).

As will be appreciated by one skilled in the art, in a first embodiment,the present invention may be a system; in a second embodiment, thepresent invention may be a method; and in a third embodiment, thepresent invention may be a computer program product.

Any of the components of an embodiment of the present invention can bedeployed, managed, serviced, etc. by a service provider that offers todeploy or integrate computing infrastructure with respect to monitoringdisk utilization at an object level. Thus, an embodiment of the presentinvention discloses a process for supporting computer infrastructure,where the process includes providing at least one support service for atleast one of integrating, hosting, maintaining and deployingcomputer-readable code (e.g., program code 814) in a computer system(e.g., computer 102) including one or more processors (e.g., CPU 802),wherein the processor(s) carry out instructions contained in the codecausing the computer system to monitor disk utilization at an objectlevel. Another embodiment discloses a process for supporting computerinfrastructure, where the process includes integrating computer-readableprogram code into a computer system including a processor. The step ofintegrating includes storing the program code in a computer-readablestorage device of the computer system through use of the processor. Theprogram code, upon being executed by the processor, implements a methodof monitoring disk utilization at an object level.

While it is understood that program code 814 for monitoring diskutilization at an object level may be deployed by manually loadingdirectly in client, server and proxy computers (not shown) via loading acomputer-readable storage medium (e.g., computer data storage unit 812),program code 814 may also be automatically or semi-automaticallydeployed into computer 102 by sending program code 814 to a centralserver or a group of central servers. Program code 814 is thendownloaded into client computers (e.g., computer 102) that will executeprogram code 814. Alternatively, program code 814 is sent directly tothe client computer via e-mail. Program code 814 is then either detachedto a directory on the client computer or loaded into a directory on theclient computer by a button on the e-mail that executes a program thatdetaches program code 814 into a directory. Another alternative is tosend program code 814 directly to a directory on the client computerhard drive. In a case in which there are proxy servers, the processselects the proxy server code, determines on which computers to placethe proxy servers' code, transmits the proxy server code, and theninstalls the proxy server code on the proxy computer. Program code 814is transmitted to the proxy server and then it is stored on the proxyserver.

Another embodiment of the invention provides a method that performs theprocess steps on a subscription, advertising and/or fee basis. That is,a service provider, such as a Solution Integrator, can offer to create,maintain, support, etc. a process of monitoring disk utilization at anobject level. In this case, the service provider can create, maintain,support, etc. a computer infrastructure that performs the process stepsfor one or more customers. In return, the service provider can receivepayment from the customer(s) under a subscription and/or fee agreement,and/or the service provider can receive payment from the sale ofadvertising content to one or more third parties.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) (memory 804 and computer data storageunit 812) having computer readable program instructions 814 thereon forcausing a processor (e.g., CPU 802) to carry out aspects of the presentinvention.

The computer readable storage medium (i.e., computer readable storagedevice) can be a tangible device that can retain and store instructions(e.g., program code 814) for use by an instruction execution device. Thecomputer readable storage medium may be, for example, but is not limitedto, an electronic storage device, a magnetic storage device, an opticalstorage device, an electromagnetic storage device, a semiconductorstorage device, or any suitable combination of the foregoing. Anon-exhaustive list of more specific examples of the computer readablestorage medium includes the following: a portable computer diskette, ahard disk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory), a staticrandom access memory (SRAM), a portable compact disc read-only memory(CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk,a mechanically encoded device such as punch-cards or raised structuresin a groove having instructions recorded thereon, and any suitablecombination of the foregoing. A computer readable storage medium and acomputer readable storage device, as used herein, are not to beconstrued as being transitory signals per se, such as radio waves orother freely propagating electromagnetic waves, electromagnetic wavespropagating through a waveguide or other transmission media (e.g., lightpulses passing through a fiber-optic cable), or electrical signalstransmitted through a wire.

Computer readable program instructions (e.g., program code 814)described herein can be downloaded to respective computing/processingdevices (e.g., computer 102) from a computer readable storage medium orto an external computer or external storage device (e.g., computer datastorage unit 812) via a network (not shown), for example, the Internet,a local area network, a wide area network and/or a wireless network. Thenetwork may comprise copper transmission cables, optical transmissionfibers, wireless transmission, routers, firewalls, switches, gatewaycomputers and/or edge servers. A network adapter card (not shown) ornetwork interface (not shown) in each computing/processing devicereceives computer readable program instructions from the network andforwards the computer readable program instructions for storage in acomputer readable storage medium within the respectivecomputing/processing device.

Computer readable program instructions (e.g., program code 814) forcarrying out operations of the present invention may be assemblerinstructions, instruction-set-architecture (ISA) instructions, machineinstructions, machine dependent instructions, microcode, firmwareinstructions, state-setting data, or either source code or object codewritten in any combination of one or more programming languages,including an object oriented programming language such as Smalltalk,C++or the like, and conventional procedural programming languages, suchas the “C” programming language or similar programming languages. Thecomputer readable program instructions may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider). In some embodiments, electronic circuitry including, forexample, programmable logic circuitry, field-programmable gate arrays(FPGA), or programmable logic arrays (PLA) may execute the computerreadable program instructions by utilizing state information of thecomputer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations (e.g., FIG. 2 and FIGS. 3A-3B) and/or blockdiagrams (e.g., FIG. 1 and FIG. 8) of methods, apparatus (systems), andcomputer program products according to embodiments of the invention. Itwill be understood that each block of the flowchart illustrations and/orblock diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerreadable program instructions (e.g., program code 814).

These computer readable program instructions may be provided to aprocessor (e.g., CPU 802) of a general purpose computer, special purposecomputer, or other programmable data processing apparatus (e.g.,computer 102) to produce a machine, such that the instructions, whichexecute via the processor of the computer or other programmable dataprocessing apparatus, create means for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks. Thesecomputer readable program instructions may also be stored in a computerreadable storage medium (e.g., computer data storage unit 812) that candirect a computer, a programmable data processing apparatus, and/orother devices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions (e.g., program code 814) mayalso be loaded onto a computer (e.g. computer 102), other programmabledata processing apparatus, or other device to cause a series ofoperational steps to be performed on the computer, other programmableapparatus or other device to produce a computer implemented process,such that the instructions which execute on the computer, otherprogrammable apparatus, or other device implement the functions/actsspecified in the flowchart and/or block diagram block or blocks.

In one embodiment, memory 804 is ROM and computer 102 is a specialpurpose computer, where the ROM includes instructions of program code814 that are executed by CPU 802 via ROM 804 to monitor disk utilizationat an object level.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

While embodiments of the present invention have been described hereinfor purposes of illustration, many modifications and changes will becomeapparent to those skilled in the art. Accordingly, the appended claimsare intended to encompass all such modifications and changes as fallwithin the true spirit and scope of this invention.

What is claimed is:
 1. A method of monitoring disk utilization at anobject level, the method comprising the steps of: a computer determiningat a first time a first size of an object in a System i platform bycalling an application programming interface (API), the object being (1)an object in an integrated file system (IFS), or (2) a library thatincludes other objects which are named storage spaces in the System iplatform; the computer determining at a second time a second size of theobject by calling the API, the second time being subsequent to the firsttime and the second size being greater than the first size; the computerdetermining a difference between the first and second sizes; thecomputer determining the difference exceeds a threshold difference;based on the difference exceeding the threshold difference, the computersending an alert about the object having a growth in size that exceedsthe threshold difference, the alert indicating the growth at a level ofthe object, which is different from a growth at a level of an auxiliarystorage pool in the System i platform; the computer periodically andautomatically monitoring sizes of libraries in the System i platform,which determines sizes of the libraries at multiple dates, and whichstores the sizes of the libraries at the multiple dates in a datarepository; the computer receiving via an interface a selection from auser of a comparison of sizes of the libraries at a start date and anend date; the computer receiving via the interface the start date andthe end date entered by the user, the start and end dates being includedin the multiple dates; the computer retrieving from the data repositorythe sizes of the libraries at the start and end dates; the computerdetermining differences between the sizes of the libraries at the startdate and respective sizes of the libraries at the end date; the computerpresenting the differences between the sizes of the libraries at thestart and end dates and presenting the sizes of the libraries at thestart and end dates; and the computer generating and sending a reportthat includes the differences between the sizes of the libraries at thestart and end dates and includes the sizes of the libraries at the startand end dates.
 2. The method of claim 1, wherein the step of determiningthe first size of the object includes determining the first size withoutemploying commands RTVDSKINF, PRTDSKINF, RTVDIRINF, or PRTDIRINF, andwherein the step of determining the second size of the object includesdetermining the second size without employing commands RTVDSKINF,PRTDSKINF, RTVDIRINF, or PRTDIRINF.
 3. The method of claim 1, furthercomprising the steps of: the computer receiving via the interface aselection by a user of a real time comparison of sizes of objects in anintegrated file system (IFS) in the System i platform at the start dateand a current time; the computer receiving via the interface the startdate entered by the user; the computer calling an applicationprogramming interface (API) in the System i platform, which obtains thesizes of the objects at the start date and the current time; thecomputer determining differences between the sizes of the objects at thestart date and respective sizes of the objects at the current time; thecomputer presenting the differences between the sizes of the objects atthe start date and the current time and presenting the sizes of theobjects at the start date and the current time; and the computergenerating and sending a second report that includes the differencesbetween the sizes of the objects at the start date and the current timeand includes the sizes of the objects at the start date and the currenttime.
 4. The method of claim 1, further comprising the steps of: thecomputer receiving via the interface a selection from a user of a realtime comparison of sizes of the libraries at the start date and acurrent time; the computer receiving via the interface the start dateentered by the user; the computer calling an application programminginterface (API) in the System i platform, which obtains the sizes of thelibraries at the start date and the current time; the computerdetermining differences between the sizes of the libraries at the startdate and respective sizes of the libraries at the current time; thecomputer presenting the differences between the sizes of the librariesat the start date and the current time and presenting the sizes of thelibraries at the start date and the current time; and the computergenerating and sending a second report that includes the differencesbetween the sizes of the libraries at the start date and the currenttime and includes the sizes of the libraries at the start date and thecurrent time.
 5. The method of claim 1, wherein the steps of determiningthe first and second sizes, and the step of determining the differencedo not include manually logging onto a system in the System i platformto determine the first and second sizes.
 6. The method of claim 1,further comprising the step of: providing at least one support servicefor at least one of creating, integrating, hosting, maintaining, anddeploying computer-readable program code in the computer, the programcode being executed by a processor in the computer to implement thesteps of determining the first size of the object at the first time,determining the second size of the object at the second time,determining the difference between the first and second sizes,determining the difference between the first and second sizes exceedsthe threshold difference, sending the alert, periodically andautomatically monitoring the sizes of the libraries, receiving theselection of the comparison of the sizes of the libraries at the startdate and the end date, receiving the start date and the end date,retrieving the sizes of the libraries at the start and end dates,determining the differences between the sizes of the libraries at thestart date and the respective sizes of the libraries at the end date,presenting the differences between the sizes of the libraries at thestart and end dates, presenting the sizes of the libraries at the startand end dates, and generating and sending the report.
 7. A computersystem comprising: a central processing unit (CPU); a memory coupled tothe CPU; and a computer-readable storage device coupled to the CPU, thestorage device containing instructions that are executed by the CPU viathe memory to implement a method of automatically monitoring diskutilization at an object level, the method comprising the steps of: thecomputer system determining at a first time a first size of an object ina System i platform by calling an application programming interface(API), the object being (1) an object in an integrated file system(IFS), or (2) a library that includes other objects which are namedstorage spaces in the System i platform; the computer system determiningat a second time a second size of the object by calling the API, thesecond time being subsequent to the first time and the second size beinggreater than the first size; the computer system determining adifference between the first and second sizes; the computer systemdetermining the difference exceeds a threshold difference; based on thedifference exceeding the threshold difference, the computer systemsending an alert about the object having a growth in size that exceedsthe threshold difference, the alert indicating the growth at a level ofthe object, which is different from a growth at a level of an auxiliarystorage pool in the System i platform; the computer system periodicallyand automatically monitoring sizes of libraries in the System iplatform, which determines sizes of the libraries at multiple dates, andwhich stores the sizes of the libraries at the multiple dates in a datarepository; the computer system receiving via an interface a selectionfrom a user of a comparison of sizes of the libraries at a start dateand an end date; the computer system receiving via the interface thestart date and the end date entered by the user, the start and end datesbeing included in the multiple dates; the computer system retrievingfrom the data repository the sizes of the libraries at the start and enddates; the computer system determining differences between the sizes ofthe libraries at the start date and respective sizes of the libraries atthe end date; the computer system presenting the differences between thesizes of the libraries at the start and end dates and presenting thesizes of the libraries at the start and end dates; and the computersystem generating and sending a report that includes the differencesbetween the sizes of the libraries at the start and end dates andincludes the sizes of the libraries at the start and end dates.
 8. Thecomputer system of claim 7, wherein the step of determining the firstsize of the object includes determining the first size without employingcommands RTVDSKINF, PRTDSKINF, RTVDIRINF, or PRTDIRINF, and wherein thestep of determining the second size of the object includes determiningthe second size without employing commands RTVDSKINF, PRTDSKINF,RTVDIRINF, or PRTDIRINF.
 9. The computer system of claim 7, wherein themethod further comprises the steps of: the computer receiving via theinterface a selection by a user of a real time comparison of sizes ofobjects in an integrated file system (IFS) in the System i platform atthe start date and a current time; the computer receiving via theinterface the start date entered by the user; the computer calling anapplication programming interface (API) in the System i platform, whichobtains the sizes of the objects at the start date and the current time;the computer determining differences between the sizes of the objects atthe start date and respective sizes of the objects at the current time;the computer presenting the differences between the sizes of the objectsat the start date and the current time and presenting the sizes of theobjects at the start date and the current time; and the computergenerating and sending a second report that includes the differencesbetween the sizes of the objects at the start date and the current timeand includes the sizes of the objects at the start date and the currenttime.
 10. The computer system of claim 7, wherein the method furthercomprises the steps of: the computer receiving via the interface aselection from a user of a real time comparison of sizes of thelibraries at the start date and a current time; the computer receivingvia the interface the start date entered by the user; the computercalling an application programming interface (API) in the System iplatform, which obtains the sizes of the libraries at the start date andthe current time; the computer determining differences between the sizesof the libraries at the start date and respective sizes of the librariesat the current time; the computer presenting the differences between thesizes of the libraries at the start date and the current time andpresenting the sizes of the libraries at the start date and the currenttime; and the computer generating and sending a second report thatincludes the differences between the sizes of the libraries at the startdate and the current time and includes the sizes of the libraries at thestart date and the current time.
 11. The computer system of claim 7,wherein the steps of determining the first and second sizes, and thestep of determining the difference do not include manually logging ontoa system in the System i platform to determine the first and secondsizes.
 12. A computer program product, comprising: a computer-readablestorage device; and a computer-readable program code stored in thecomputer-readable storage device, the computer-readable program codecontaining instructions that are executed by a central processing unit(CPU) of a computer system to implement a method of automaticallymonitoring disk utilization at an object level, the method comprisingthe steps of: the computer system determining at a first time a firstsize of an object in a System i platform by calling an applicationprogramming interface (API), the object being (1) an object in anintegrated file system (IFS), or (2) a library that includes otherobjects which are named storage spaces in the System i platform; thecomputer system determining at a second time a second size of the objectby calling the API, the second time being subsequent to the first timeand the second size being greater than the first size; the computersystem determining a difference between the first and second sizes; thecomputer system determining the difference exceeds a thresholddifference; based on the difference exceeding the threshold difference,the computer system sending an alert about the object having a growth insize that exceeds the threshold difference, the alert indicating thegrowth at a level of the object, which is different from a growth at alevel of an auxiliary storage pool in the System i platform; thecomputer system periodically and automatically monitoring sizes oflibraries in the System i platform, which determines sizes of thelibraries at multiple dates, and which stores the sizes of the librariesat the multiple dates in a data repository; the computer systemreceiving via an interface a selection from a user of a comparison ofsizes of the libraries at a start date and an end date; the computersystem receiving via the interface the start date and the end dateentered by the user, the start and end dates being included in themultiple dates; the computer system retrieving from the data repositorythe sizes of the libraries at the start and end dates; the computersystem determining differences between the sizes of the libraries at thestart date and respective sizes of the libraries at the end date; thecomputer system presenting the differences between the sizes of thelibraries at the start and end dates and presenting the sizes of thelibraries at the start and end dates; and the computer system generatingand sending a report that includes the differences between the sizes ofthe libraries at the start and end dates and includes the sizes of thelibraries at the start and end dates.
 13. The computer program productof claim 12, wherein the step of determining the first size of theobject includes determining the first size without employing commandsRTVDSKINF, PRTDSKINF, RTVDIRINF, or PRTDIRINF, and wherein the step ofdetermining the second size of the object includes determining thesecond size without employing commands RTVDSKINF, PRTDSKINF, RTVDIRINF,or PRTDIRINF.
 14. The computer program product of claim 12, wherein themethod further comprises the steps of: the computer receiving via theinterface a selection by a user of a real time comparison of sizes ofobjects in an integrated file system (IFS) in the System i platform atthe start date and a current time; the computer receiving via theinterface the start date entered by the user; the computer calling anapplication programming interface (API) in the System i platform, whichobtains the sizes of the objects at the start date and the current time;the computer determining differences between the sizes of the objects atthe start date and respective sizes of the objects at the current time;the computer presenting the differences between the sizes of the objectsat the start date and the current time and presenting the sizes of theobjects at the start date and the current time; and the computergenerating and sending a second report that includes the differencesbetween the sizes of the objects at the start date and the current timeand includes the sizes of the objects at the start date and the currenttime.
 15. The computer program product of claim 12, wherein the methodfurther comprises the steps of: the computer receiving via the interfacea selection from a user of a real time comparison of sizes of thelibraries at the start date and a current time; the computer receivingvia the interface the start date entered by the user; the computercalling an application programming interface (API) in the System iplatform, which obtains the sizes of the libraries at the start date andthe current time; the computer determining differences between the sizesof the libraries at the start date and respective sizes of the librariesat the current time; the computer presenting the differences between thesizes of the libraries at the start date and the current time andpresenting the sizes of the libraries at the start date and the currenttime; and the computer generating and sending a second report thatincludes the differences between the sizes of the libraries at the startdate and the current time and includes the sizes of the libraries at thestart date and the current time.
 16. The computer program product ofclaim 12, wherein the steps of determining the first and second sizes,and the step of determining the difference do not include manuallylogging onto a system in the System i platform to determine the firstand second sizes.
 17. A method of automatically monitoring diskutilization at an object level, the method comprising the steps of: acomputer determining at a first time a first size of an object bycalling an application programming interface (API) provided by acomputing platform, the object being (1) a directory in a hierarchicalfile system provided by the computing platform, or (2) a library thatincludes other objects which are named storage spaces in the computingplatform; the computer determining at a second time a second size of theobject by calling the API, the second time being subsequent to the firsttime and the second size being greater than the first size; the computerdetermining a difference between the first and second sizes; thecomputer determining the difference exceeds a threshold difference;based on the difference exceeding the threshold difference, the computersending an alert about the object having a growth in size that exceedsthe threshold difference, the alert indicating the growth at a level ofthe object; the computer periodically and automatically monitoring sizesof libraries in the computing platform, which determines sizes of thelibraries at multiple dates, and which stores the sizes of the librariesat the multiple dates in a data repository; the computer receiving viaan interface a selection from a user of a comparison of sizes of thelibraries at a start date and an end date; the computer receiving viathe interface the start date and the end date entered by the user, thestart and end dates being included in the multiple dates; the computerretrieving from the data repository the sizes of the libraries at thestart and end dates; the computer determining differences between thesizes of the libraries at the start date and respective sizes of thelibraries at the end date; the computer presenting the differencesbetween the sizes of the libraries at the start and end dates andpresenting the sizes of the libraries at the start and end dates; andthe computer generating and sending a report that includes thedifferences between the sizes of the libraries at the start and enddates and includes the sizes of the libraries at the start and enddates.
 18. The method of claim 17, wherein the steps of determining thefirst size and determining the second size do not employ commandsRTVDSKINF, PRTDSKINF, RTVDIRINF, or PRTDIRINF.